home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The CICA Windows Explosion!
/
The CICA Windows Explosion! - Disc 2.iso
/
access
/
secure.zip
/
SRC
/
READ.ME
next >
Wrap
Text File
|
1991-11-01
|
2KB
|
50 lines
/* ********** SECURE Lan Manager security checking for SQL Server *******
*
* This program is an adaptation of the standard pass-through gateway.
* It implements a security integration layer between Lan Manager
* and SQL Server. On as connection event (in SECURECBS.C) Lan Manager
* is queried for the name of the user on the other end of the pipe.
* This username is compared to the requested SQL Server login name,
* and the login is rejected if the two don't match.
*
* If the /F flag is given at startup, all language events will be written
* to the GDK log file prior to being passed on to SQL Server.
*
* Usage: secure -S<machine_name> -p<pipe_name> -L<logfile> -N
*
* where
* machine_name = Target SQL Server name on network
* (default is local machine)
*
* pipe_name = Input pipe name for DB-Lib clients
* (default is \pipe\sql\query)
*
* logfile = Name of GDK log file
* (default is gateway.log if /F is
* given without a filename)
*
* -N = turns off login checking (if you just want
* use request logging)
*
* If you run the SECURE application on the same machine as SQL Server,
* you can have the GDK listen on the default pipe name, \pipe\sql\query
* and set SQL Server itself to listen on a different, secured
* pipe name. To start SQL Server listening on a different pipe, use
*
* sqlservr -d c:\sql\data\master.dat -pPipePath
*
* This will start SQL Server listening on the pipe \pipe\PipePath\query
* You will also need to add an entry to OS2.INI to have SECURE itself
* point to this pipe on the back end. In this case, the machine_name
* used in starting up the GDK will correspond to an entry in the OS2.INI
* on the same machine. See the Appendix to the GDK Programmer's Reference
* for details on how to set OS2.INI.
*
* By configuring the SECURE application this way, client configurations
* will not need to change-- they will connect to the default pipe name.
*
* This application requires the LAN Manager 2.0 Programmer's Toolkit
* for compilation and linking.
*
***********************************************************************/